docs(CSM-341): explain Android double package cause in Testing Distribution FAQ#3
docs(CSM-341): explain Android double package cause in Testing Distribution FAQ#3arcappcircle wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR adds documentation explaining that enabling both Gradle signing and Appcircle's Android Sign build step produces two separately signed APK artifacts. Caution notes were added to the Android Sign and Android Build docs, plus a new FAQ entry in the Testing Distribution profile doc. ChangesAndroid dual-signing documentation
Sequence Diagram(s)No sequence diagram generated as these are documentation-only text additions. Poem
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Warning Tools execution failed with the following error: Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error) Comment |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
appcircle-docs | 650cbb5 | Commit Preview URL Branch Preview URL |
Jul 07 2026, 12:00 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
appcircle-docs | 650cbb5 | Commit Preview URL Branch Preview URL |
Jul 07 2026, 12:00 PM |
Summary
Expands the Testing Distribution FAQ entry "No files or multiple files were received from autodistribute" to explain why two Android packages are distributed and how to avoid it.
When an Android project defines its own gradle sign config and the Appcircle Android Sign step is enabled, the build produces two signed APK artifacts and AutoDistribute sends both to the distribution profile (this happens even with auto-send). The doc now documents the two-binary origin, the single-signing-path resolution, and the AAB convert option via Auto Re-sign.
Context
Changes
docs/testing-distribution/create-or-select-a-distribution-profile.md- new "Why two Android packages are distributed" subsection + AAB convert note under the FAQ.docs/workflows/android-specific-workflow-steps/android-build.md- caution note cross-linking the FAQ section.docs/workflows/android-specific-workflow-steps/android-sign.md- caution note cross-linking the FAQ section.Migrated from appcircle-docusaurus#1249.
Created on behalf of ozcan@appcircle.io via Arc.
Summary by CodeRabbit